Blog

Luis Majano

October 10, 2009

Spread the word


Share your thoughts

I just committed two critical fixes to the 3.0.0 Beta 2 core.  I have also updated the download bits, so I recommend downloading the new bits to have these following fixes applied:

  1. ColdBox cache was not purging object metadata successfully, thus making the cache do unecessary object recreations once objects expired. Ticket #883
  2. Flash RAM objects where not keeping objects once web flows where activated via the "keep()" methods.  Ticket #882
Enjoy!

Add Your Comment

(2)

Oct 11, 2009 04:17:31 UTC

by John Whish

Great work Luis - ColdBox 3 is shaping up to be a killer release!

Oct 11, 2009 10:37:05 UTC

by Luis Majano

Thanks John!!

We are really moving forward with 3.0.0. It will take time but it is getting there.

Recent Entries

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.

For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.

Maria Jose Herrera
Maria Jose Herrera
September 18, 2026
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026